Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix ChecksumIntegrationTest #4798

Merged
merged 2 commits into from
Dec 22, 2023
Merged

Fix ChecksumIntegrationTest #4798

merged 2 commits into from
Dec 22, 2023

Conversation

dagnir
Copy link
Contributor

@dagnir dagnir commented Dec 21, 2023

  • Some tests specificy a part number, but CRT may do a range get under the hood. S3 will throw an error if both a range and part number are specified. This is an issue that needs to be fixed in CRT, but part number is not required in this test, so removing it.

  • Rename test file to CrtCheckIntegrationTest so it gets added to CRT test suite

  • This PR also reverts 045bcc4, which itself reverted the change that uncovered this issue.

Motivation and Context

Modifications

Testing

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Checklist

  • I have read the CONTRIBUTING document
  • Local run of mvn install succeeds
  • My code follows the code style of this project
  • My change requires a change to the Javadoc documentation
  • I have updated the Javadoc documentation accordingly
  • I have added tests to cover my changes
  • All new and existing tests passed
  • I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
  • My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

  • I confirm that this pull request can be released under the Apache 2 license

- Some tests specificy a part number, but CRT may do a range get under the hood.
  S3 will throw an error if both a range and part number are specified. This is
an issue that needs to be fixed in CRT, but part number is not required in this
test, so removing it.

 - Rename test file to CrtCheckIntegrationTest so it gets added to CRT test
   suite
@dagnir dagnir requested a review from a team as a code owner December 21, 2023 21:23
@dagnir dagnir force-pushed the dongie/fix-crt-checksum-test branch from 694cef6 to 29aa8a9 Compare December 21, 2023 23:06
@dagnir dagnir enabled auto-merge (squash) December 21, 2023 23:06
@dagnir dagnir merged commit aa51b12 into master Dec 22, 2023
13 checks passed
Copy link

sonarcloud bot commented Dec 22, 2023

Quality Gate Passed Quality Gate passed

The SonarCloud Quality Gate passed, but some issues were introduced.

3 New issues
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants